This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: java.library.path problem with JVM ~Umberto Nongeroson 9.Oct.02 07:40 PM a Web browser Domino Server 6.0Windows NT
My point was that Domino itself does not efect the way in which the JVM changes the PATH setting to come up with java.library.path.
What does the sun.boot.library.path say?
I have a suspicion about what may be happening, but I will need to do some testing to verify that. In the mean time, I suggest you use the servlet settings in the Server document instead of JavaUserClasses. That's what they are for. In this case, I expect that JavaUserClasses is actually hurting you due to internal JVM differences from 1.1.8 to 1.3.1 and the why in which we handle JavaUserClasses.